Apparatus and methods for improved packet flow mobility

ABSTRACT

Methods and apparatus for improved packet data flow mobility and packet data distribution and collection across heterogeneous networks. In one embodiment, a source device with one or more wireless interfaces receives data to be transmitted to a target device. The device sequences the received data with corresponding packet sequence numbers according to characteristics of the service providing the data. The sequenced data is classified according to application/service requirements (e.g., minimum Quality of Service requirements, service type, etc.). The classified data is assigned to available network interfaces, which can support the classifications of the data. The data is transmitted over the assigned network interfaces to the corresponding receiving interface. The data is collected and reassembled according to the packet sequence number at the target destination.

PRIORITY

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 61/637,198 entitled “APPARATUS AND METHODS FOR IMPROVED IP FLOWMOBILITY AND WLAN OFFLOADING” filed Apr. 23, 2012, which is incorporatedby reference herein in its entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention relates generally to operation withinheterogeneous wireless systems such as, for example, hybrid networkoperation in which client or user devices can communicate using any oneof two or more networks. More particularly, in one exemplary aspect, thepresent invention is directed to methods and apparatus for dynamicallyallocating data flows across heterogeneous networks.

2. Description of Related Technology

Mobile client devices have evolved from single-radio devices tomultiple-radio devices configured to support different radio accesstechnologies. For example, an exemplary mobile cellular device mayinclude both a cellular radio (e.g., Long Term Evolution (LTE)) as wellas a wireless local area network (WLAN) radio (e.g., IEEE 802.11-basedwireless).

Consider for example LTE, which is a Radio Access Technology (RAT)standardized under the Third Generation Partnership Project (3GPP). LTEwas first codified within the 3GPP Release 8 Evolved Packet System(EPS); Release 8 implementations do not allow simultaneous operation ofmultiple radio access technologies (i.e., a mobile device cannot accessthe same Packet Data Network (PDN) via the multiple radio interfaces).Instead, Release 8 implementations require the user of the mobile deviceto establish a single PDN connection, or may establish multiplesimultaneous PDN connections through the same radio access system, butnot through different radio access systems. Accordingly, a mobile devicecould not treat individual packets of (in this case, Internet Protocol(IP)) flows within a PDN connection separately across differentavailable radio access systems. Therefore, when handing over from onceaccess network to another, the mobile device would be required to moveall IP flows from within a given PDN connection together to the otheraccess network.

Furthermore, the set of possible applications running on the mobiledevice that may require use of a device's radio are diversified. Whilesome of these applications may be suited for radio access systems withstringent Quality of Service (QoS) requirements (e.g. 3GPP), some otherapplications may be suited to run over the other available radio(s)access systems. However, current implementations do not effectivelyallow for application/services to take advantage of all the availableresources, which may suitable for providing service for theapplications/services.

Accordingly, improved apparatus and methods are needed for mobiledevices to allow for enhanced capability, including for example dynamicallocation of data flows across the available radio access technologiesso as to enhance a user's experience, while also ideally optimizing theconnectivity costs of network operators.

SUMMARY OF THE INVENTION

The present invention satisfies the aforementioned needs by providing,inter alia, improved apparatus and method for dynamic IP Flow mobilityacross heterogeneous networks.

In a first aspect of the invention, a method for dynamically allocatingdata flows across heterogeneous network interfaces is disclosed. In oneembodiment, the method includes: sequencing portions of data to betransmitted over two or more interfaces; classifying the data accordingto one or more parameters; assigning the portions of the data to the twoor more interfaces based at least on part on the classification; andtransmitting the portions of data over the assigned two or moreinterfaces.

In a second aspect of the invention, a client or user device isdisclosed. In one embodiment, the device is capable of dynamicallyallocating a packet corresponding to a service flow or IP flow acrossheterogeneous networks, and includes: a processor; at least first andsecond wireless interfaces in data communication with the processor; anda storage device in data communication with the processor, the storagedevice comprising at least one computer program. In one variant, theprogram is configured to, when executed on the processor dynamicallyallocate packet data flows across the first and second wirelessinterfaces by at least: sequencing portions of data to be transmittedover first and second interfaces; characterizing the data according toone or more parameters; assigning the portions of the data to the firstand interfaces based at least on part on the characterization; andtransmitting the assigned portions of data over the interfaces.

In another embodiment, the device is a mobile user wireless apparatusthat includes a processor; at least first and second wireless interfacesin data communication with the processor; and logic configured todynamically allocate packet data flows across the first and secondwireless interfaces by at least: obtaining feedback information from areceiver apparatus regarding the quality or reliability of at least oneof the first and second wireless interfaces; selectively allocating atleast portions of a first packet data flow over at least one of thefirst and second wireless interfaces based at least in part on thefeedback information; and transmitting the allocated at least portionsof the data flow over the at least one interface based on the selectiveallocation.

In a third aspect of the invention, wireless network apparatus isdisclosed. In one embodiment, the apparatus includes a processor; atleast first and second wireless interfaces in data communication withthe processor; and computerized logic configured to dynamically allocatepacket data flows across the first and second wireless interfaces by atleast selectively allocating at least portions of a first packet dataflow over at least one of the first and second wireless interfaces basedat least in part on information relating to one or more attributes ofthe first packet data flow, and transmitting the allocated at leastportions of the data flow over the at least one interface based on theselective allocation. In one variant, the computerized logic is furtherconfigured to operate substantially at the network layer of the mobileapparatus so as to be independent of lower-layer functions.

In a fourth aspect of the invention, network apparatus is disclosedwhich includes a processor, at least first and second wirelessinterfaces in data communication with the processor; and a storagedevice in data communication with the processor. In one embodiment, thestorage device comprising at least one computer program configured to,when executed on the processor, dynamically allocate packet data flowsacross the first and second wireless interfaces by at least: receivingvia one of the first and second wireless interfaces a request for apacket data flow from a mobile device; sequencing portions of data flowto be transmitted over first and second interfaces; characterizing thedata according to one or more parameters; assigning the portions of thedata to the first and interfaces based at least on part on thecharacterization; and transmitting the assigned portions of data overthe interfaces to the requesting mobile device.

In another embodiment, the network apparatus includes logic disposed ata network layer thereof and configured to selectively route packetsbelonging to a common Internet Protocol (IP) data flow across two ormore heterogeneous radio access technology interfaces accessible to thenetwork apparatus to respective two or more heterogeneous radio accesstechnology interfaces of a mobile wireless device with which the networkserver apparatus communicates.

In a fifth aspect of the invention, a computer-readable storageapparatus is disclosed.

In a sixth aspect of the invention, a heterogeneous wireless system isdisclosed.

Other features and advantages of the present invention will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a logical block diagram illustrating an exemplaryheterogeneous network system useful in conjunction with the presentinvention.

FIG. 2 is a logical block diagram illustrating an exemplary prior artInternet Protocol (IP) flow mobility operation.

FIG. 3 is a logical block diagram illustrating an exemplary improvedheterogeneous IP flow mobility configured in accordance with the presentinvention.

FIG. 4 is a functional block diagram of an exemplary implementation ofthe improved heterogeneous IP flow mobility of FIG. 3.

FIG. 5 is a logical block diagram of an exemplary protocol structure forimproved IP flow mobility and content distribution in accordance withthe present invention.

FIG. 6 is a logical block diagram of an exemplary cross-network contentdistribution communicating to a client device over heterogeneousnetworks in accordance with the present invention.

FIG. 7 is a logical flow diagram detailing one embodiment of ageneralized method for dynamically allocating data flows across multiplenetworks, in accordance with the present invention.

FIG. 8 is a logical flow diagram of an exemplary implementation of FIG.7

FIG. 9 is functional block diagram of an exemplary user device apparatusconfigured to dynamically allocate data flows across heterogeneousnetworks, in accordance with the present invention.

FIG. 10 is a functional block diagram of an exemplary server apparatussupporting dynamic allocation of data flow for a client device acrossheterogeneous networks, in accordance with the present invention.

All Figures © Copyright 2012 Apple Inc. All rights reserved.

DETAILED DESCRIPTION OF THE INVENTION

Reference is now made to the drawings, wherein like numerals refer tolike parts throughout.

Overview

Mobile devices can support connections to multiple heterogeneous radioaccess technologies, such as for example Long Term Evolution LTEnetworks and IEEE 802.11-based wireless local access networks.Additionally, mobile devices implementing packet data (e.g., IP data)flow mobility functionality can transfer IP data flows across one radioaccess technology to another radio access technology in order to, forexample, provide more reliable service or free up network resources.

However, current IP flow mobility functionality must route all packetsbelonging to the same IP flow to a single radio access technology, andcannot spread packets belonging to the same IP flow across multipleradio access technologies available on the mobile device. Since themobile device cannot take advantage of all radio access technologiesavailable to the device, various embodiments of the present inventionare directed at improvement of IP flow mobility and WLAN offloadingschemes across heterogeneous networks, including use of two or more airinterfaces available to a mobile device (or network apparatus such as abase station).

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary embodiments and aspects of the present invention are nowdescribed in detail. While these embodiments and aspects are primarilydiscussed in the context of heterogeneous networks of Long TermEvolution (LTE) cellular network and a WLAN (e.g., IEEE 802.11-basedwireless network), it will be recognized by those of ordinary skill thatthe present invention is not so limited, and can be used with othercellular and/or wireless access technologies such as TD-LTE(Time-Division Long-Term Evolution), TD-LTE-Advanced, TD-SCDMA (TimeDivision Synchronous Code Division Multiple Access) and Global Systemfor Mobile Communications (GSM), General Packet Radio Service (GPRS),Code Division Multiple Access (CDMA) 2000 1X, CDMA 1X EVDO (EvolutionData Optimized), and Worldwide Interoperability for Microwave Access(WiMAX). In fact, the various aspects of the invention are useful incombination with any network or combinations thereof (cellular,wireless, wireline, or otherwise) that can benefit from allocation ofdata flows across heterogeneous networks.

Existing Heterogeneous Networks Technologies

In the following discussion, an exemplary heterogeneous network isillustrated comprising a cellular radio system that includes a networkof radio cells each served by a transmitting station, known as a cellsite or base station (BS), as well as wireless local access network(WLAN), such an 802.11-based network which may be served using an accesspoint (AP). The radio network provides wireless communications servicefor a plurality of mobile station (MS) devices.

With respect to cellular radio systems, the network of BSs working incollaboration allows for wireless service, which is greater than theradio coverage provided by a single serving BS. The individual BSs areconnected to a Core Network, which includes additional controllers forresource management, and is in some cases capable of accessing othernetwork systems (such as the Internet, other cellular networks, etc.).In addition, the MS may able to be connected to other BSs implementingvia other wireless communication technologies. For example, a MS mayhave network access to a Long Term Evolution (LTE) network and an802.11-based network, each of which is capable of implementing a Qualityof Service (QoS) policy.

As a brief aside, in the context of an LTE cellular network, the EvolvedPacket System (EPS) bearer/E-RAB (radio bearer) is the level ofgranularity for bearer-level QoS control in the Evolved Packet Core(EPC)/UMTS Terrestrial Radio Access Network (UTRAN). Service data flowsmapped to the same EPS bearer receive the same bearer-level packetforwarding treatment (e.g., scheduling policy, queue management policy,rate shaping policy, RLC configuration, etc.) One EPS bearer/E-RAB isestablished when a client device connects to a PDN; this remainsthroughout the lifetime of the PDN connection to provide the clientdevice with always-on IP connectivity to that PDN. The aforementionedbearer is referred to as the default bearer. Any additional EPC/E-RABthat is established to the same PDN is referred to as a “dedicatedbearer”. The initial bearer level QoS parameter values of the defaultbearer are assigned by the network, based on subscription data. Thedecision to establish or modify a dedicated bearer can only be taken bythe EPC, and the bearer level QoS parameter values are assigned by theEPC. An EPS bearer is referred to as a “GBR” (Guaranteed Bit Rate)bearer if dedicated network resources are permanently allocated (e.g.,by an admission control function in the eNodeB) at time of bearerestablishment or modification. Otherwise, an EPS bearer/E-RAB isreferred to as a “Non-GBR bearer”. A dedicated bearer can either be aGBR or Non-GBR bearer, while a default bearer is a Non-GBR bearer.

FIG. 1 illustrates two exemplary heterogeneous networks and a clientdevice 102, operating within the coverage of Radio Access Networks (RAN)provided by a number of base stations (BSs) 104 as well as an AccessPoint (AP) 108 of an 802.11-based system. The RAN is the collective bodyof base stations and associated network entities that are controlled bya Mobile Network Operator (MNO). The AP 108 enables the client device102 to communicate over the associated Network Entity 110. The userinterfaces to the RAN via the client devices, which in many typicalusage cases is a cellular phone or smartphone. However, as used herein,the terms “mobile station”, “mobile device”, “client device”, “userequipment”, and “user device” may include, but are not limited to,cellular telephones, smart phones (such as for example an iPhone™manufactured by the Assignee hereof), personal computers (PCs) andminicomputers, whether desktop, laptop, or otherwise, as well as mobiledevices such as handheld computers, PDAs, personal media devices (PMDs),tablet computers such as the exemplary iPad™ device manufactured by theAssignee hereof, or any combinations of the foregoing.

As shown in FIG. 1, a RAN is coupled to a Core Network 106 of the MNO.The Core Network 106 and Network Entity 110 provide both routing andservice capabilities. For example, a client device connected to a basestation can communicate via the BS, or communicate via a connected WLANAP 108. The client device can access types of services e.g., theInternet, via the Core Network or via the associated Network Entity ofthe AP 108. The Core Network performs a wide variety of functions,including without limitation, authentication of client devices,authorization of client devices for various services, billing clientdevices for provisioned services, call routing, etc.

As another brief aside, cellular networks are owned and operated by anMNO. Typically, a MS is used in a so-called “home network”; the MS'shome network is operated by the MNO and has the information necessary toauthenticate and provision service to the MS (e.g., cryptographic keysused for authentication, service agreements, billing information, etc.).However, the MS may “roam” outside of the home network; accordingly,so-called “roaming” access refers to the set of services that areprovided by a “visited network” with which the client device is notassociated. Visited networks are typically operated by a different MNOthan the MNO that a mobile device is associated with, however this isnot always true (e.g., due to business arrangements, legal regulation,etc.). Roaming services are negotiated between MNOs to providereciprocal service agreements to improve service coverage for theirsubscriber populations, respectively. For example, MNOs typicallynegotiate roaming relationships with other MNOs in different countriesto enable accessibility of voice, data and other supplementary servicesfor their subscribers when they travel internationally. In addition, theBS of the roaming network may implement a radio access technology (RAT)different from the home network BS if the client device is so equippedwith the proper network interfaces.

With respect to WLAN, WLAN links devices using some wirelessdistribution scheme (e.g., IEEE 802.11 standards), providing aconnection through an AP to the wider network such as the Internet or awide area network (WAN). An AP can be a main base station (BS), relayBS, or remote BS. In typical implementations, the main BS is directlyconnected to the wider network using a wired or optical connection suchas a broadband connection (e.g., DOCSIS modem, fiber drop, etc.). Arelay BS relays data between other relay BSs, remote BSs, and MS toeither another relay BS or main BS. The remote BS accepts connectionsfrom an MS, and relays the communication from the MS to either a relayBS or the main BS. Accordingly, WLAN provides users of MS devices withmobility to move within a local coverage area, while still beingconnected to the wider network.

IP Flow Mobility

The following discussion details an exemplary IP flow mobilityoperation. IP flow mobility allows a base station/client device to routeIP flows through different radio access networks (RAN) that areavailable in the base station or on the client device by switching fromone radio access technology to another radio access technology. The IPaddress of the client device remains the same as the user moves acrossdifferent RANs. However, existing IP flow mobility functionality doesnot allow for sharing assigned IP packets of an IP flow throughdifferent radios but instead requires that the IP packets belonging tothe same IP flow must go through a single radio. Accordingly, if thedevice switches the radio (air interface), the entire IP flow path mustbe moved to the new radio. For example, a client device may have tworadio access technologies (RAT) available; i.e., an LTE radio and an802.11-based radio (i.e., Wi-Fi). An application resident on the deviceis routing its data flow through the Wi-Fi radio, while the LTE radio isrelieved from providing this service. However, if the client devicemoves out of range of the Wi-Fi RAN (or the RAN becomes otherwiseunavailable), the client device would switch the IP flow of theapplication to the LTE RAT.

Referring now to FIG. 2, a logical block diagram of an exemplary IP flowmobility operation according to the prior art is illustrated, IP flows202, 204, 206, 208 are generated by the applications, and arecommunicated to the transmit side of the device or the base station. TheIP flows 202, 204, 206, 208 are each assigned to a respective radiointerface 210. Common examples of radio interfaces useful with thepresent invention are LTE, Global Standards for Mobile CommunicationsCode Division Multiple Access (CDMA) 2000 (CDMA2000), and 802.11-basedwireless, although it will be appreciated that any number of othertechnologies may be substituted.

As shown in FIG. 2, prior art IP flow is routed to the same radiointerface, and is not shared concurrently between the radio interfaces210. The radio interfaces 210 transmit the data of the IP flows 202,204, 206, 208 to the respective radio interfaces 212 of the receiveside. The data of the IP flows are subsequently routed to theirdestination accordingly based on the protocol used.

Exemplary IP Flow Mobility Operation

One aspect of the present invention contemplates dynamically directingindividual packets belonging to the same IP flow generated by anapplication in the device or the network across the available RATs,either concurrently or separately, as shown in FIG. 3. Specifically,FIG. 3 illustrates an exemplary embodiment of improved heterogeneous IPflow mobility process configured in accordance with principles of thepresent invention.

In one embodiment, the IP flow mobility process includes a packetsequencing function 302, as well as a content distribution function 304at the transmit side. In addition, the receive side further includes acontent collection function 306 and packet sequencing function 308. Aswill be discussed in greater detail below, the packet sequencingfunction 302 and content distribution function 304 enable an IP flow tospread across multiple radio interfaces 210, instead of requiring theentire IP flow to be only assigned to one radio interface 210 at a time(such as is shown in the prior art solution of FIG. 2). The contentcollection function 306 and packet sequencing function 308 allow for thedata transmitted over the multiple radio interfaces 210 to be properlyreceived, as discussed in greater detail below.

Referring now to FIG. 4, an exemplary implementation of the IP flowprocess of FIG. 3 is illustrated. Depending on the availability of atleast one radio connection with an acceptable radio condition (forexample, to guarantee a QoS requirement of a service flow, and/or basedon interaction with the radio resource management on each link (ifapplicable) to determine the size of the packets that can be transmittedvia each radio connection), the IP packets are classified anddistributed among the available radio connections according to FIG. 4.

As a brief aside, the Open System Interconnection (OSI) model is arepresentation of functions of a communication in terms of abstractlayers. A layer serves a layer above it, and is served by a layer belowit. According to the OSI model, the layers (ascending order from lowestlayer to highest layer) consist of the physical layer, the data linklayer, the network layer, the transport layer, etc. The InternetProtocol (IP) is classified as part of the network layer, the networklayer being responsible for path determination and logical addressing oftransmitting data.

As shown in FIG. 4, the network layer IP packets 402 belonging to thesame or different IP flows on the transmit side arrive at the PacketSequencing/Classification and QoS Enforcement block 404. In oneimplementation, the Packet Sequencing/Classification and QoS Enforcementfunction block 404 is responsible for each of the aforesaid functions;i.e., packet sequencing, packet classification, and QoS enforcement,although these functions may be distributed to one or more other devicesas well.

The packet sequencing function, in one exemplary embodiment, isresponsible for adding a sequence number indication to IP packet data toenable reorganization of the data in the correct sequence. Packetsequencing is not required when only using a single radio interface 210,as the IP flow is going through the same radio interface (and thus thereis no need guarantee the proper receive order of the packet data).However, when spreading an IP flow across multiple RATs, the packet datamay be received out of sequence, as each radio interface 210 has its owncommunication characteristics (e.g. maximum data rate, connectionquality, current transmission speed, etc.). Accordingly, packetsequencing compensates for the possible out of order delivery byenabling any re-ordering of the packets at the receiver side (or othercorrective functions).

The packet classification function, in one exemplary implementation, isresponsible for classifying and associating the incoming data packetdata according to one or more designated criteria. For example,designated criteria may include priority of the particular packet data,minimum QoS requirements, parameters related to the service generatingthe data, amount of radio resources required, etc.

The Quality of Service (QoS) enforcement function, in one variant, isresponsible for monitoring radio link measurements, and/or receivinglink quality reports periodically. The period of the report isconfigurable, and the configuration of the period may differ for each ofthe radio interfaces 408. In another implementation, the monitoringoccurs non-periodically. For example, the monitoring may occur upon therequest from the corresponding RAT radio resource management orequivalent unit, upon the occurrence of another event, or evenperiodically or randomly.

Accordingly, one salient advantage of the exemplary QoS enforcementfunction described herein is that higher priority or delay-sensitivepackets may be ensured to be routed by the Content Distribution function406 to the faster and/or more reliable radio interfaces 408. Thus,performance and reliability of transmitted these data packets isimproved. It will be appreciated that other metrics for routing may beutilized, whether alone or in conjunction with one or both of theforegoing. For instance, metrics such as connection latency may beconsidered (i.e., a given interface may have a higher data rate thananother, yet have significantly longer initial connection latency,thereby rendering it less desirable in certain cases). Batteryconservation may also be considered (e.g., a slightly slower interfacemay use appreciably less battery power, which is important for mobiledevices).

In one implementation, the Packet Sequencing/Classification and QoSEnforcement block 404 is further configured to exchange event-drivensignaling with the Consent Collection Function 412 and PacketSequencing/Duplicate Detection and Removal/Jitter Mitigation functionalblocks at the receive side. The event signaling may be implemented usingIP-layer signaling and coordination messages (e.g., sending messagesusing IP protocol such that transmission and reception of the message istransparent to the radio interfaces 408, 410) with the PacketSequencing/Duplicate Detection and Removal/Jitter Mitigation 414, inorder to optimize the distribution and collection of IP packets acrossthe various radio links.

One salient advantage of communicating the event-driven signaling isproviding the transmit side with useful feedback on the performance andreliability of the different radio links that are available fordistribution of the content. In addition, the feedback from the receiverside allows for the Packet Sequencing/Classification and QoS Enforcementblock 404 to account for the ability of the receiver side to retrieveand reconstruct the content with acceptable degradation. For example,depending on the actual effective bandwidth that may be becomeavailable, only the higher priority packets may be transmitted acrossmore reliable radio links under adverse channel conditions.

The Content Distribution function 406 receives the data (and the data'srespective classification) from the Packet Sequencing/Classification andQoS Enforcement block 404. In one embodiment, the Content Distributionfunction 406 is located at the network layer. One advantage of theContent Distribution function being disposed at the network layer ispossible independence from functions of the data link layer, for examplethe Media Access Control (MAC) layer packet data unit (PDU) schedulingand transmission functionality corresponding to each radio interface.The Content Distribution function 406 distributes the data packets toassigned radio interfaces 408.

In order to make a radio interface assignment, the Content Distributionfunction 406 may be configured to receive information and statistics ofthe radio interfaces 408. For example, the information and statisticsmay include the availability of the radio link, the quality of the radiolink, maximum sustained data rate over the radio link, reliability ofthe radio link, maximum delay over the radio link, maximum radioresource size that can be allocated over the radio link, etc. Based onthe received information, the Content Distribution function candetermine the amount of data that can be routed through each availableradio link and/or which radio links are suited to carry IP data fromparticular service. In one implementation, the Content Distributionfunction ensures that the IP packets that were already assigned fromtransmission over radio interfaces 408 that have become unavailable, arereassigned to other available radio interfaces 408, thereby mitigatingany interruption in service. In one variant, the Content Distributionfunction 406 coordinates with individual schedulers of each radiointerface 408, as some radio interfaces 408 may not be able to operateconcurrently. For example, an inter-RAT interface may restrictsimultaneous use of some of the radio interfaces 408 which the ContentDistribution function 408 can account for during distribution ofassigned IP packets.

Another salient advantage of the present invention is that headercompression schemes of IP/UPD/RTP or IP/TCP (for example Robust HeaderCompression (RoHC)) operating on the different radio links are notsignificantly impacted by the distribution function, given that theheader compression follows static and dynamic fields of the headers ofthe IP packets that are routed through a particular radio link. It willbe appreciated by those of ordinary skill however that not all radiointerface technologies support header compression as part of thebaseband processing, and the various aspects of the present inventionmay be used in either case.

The radio interfaces 408 transmit IP packets as distributed by theContent Distribution function 406 to the respective receiver side radiointerfaces 410. In one embodiment, the radio interfaces are responsiblefor monitoring metrics of the radio link of the respective receiverradio interfaces 410, such as for example a channel quality indication(CQI), SINR, and/or other useful parameters for assessing channeloperability and reliability.

Upon receiving the IP packets at the receiver radio interfaces 410, theradio interfaces 410 provide the received IP packets to the ContentCollection function 412. In one embodiment, the Content Collectionfunction 412 is responsible for controlling the receipt and collectionof the received IP packets. The Content collection function 412 trackswhether packets are received, such as by the packet sequencinginformation (e.g., an assigned sequence number embedded in each packet)associated with the received packets. Accordingly, if a packet sequencenumber is missing out of a sequence of packet sequence numbers, theContent Collection function 412 can identify which IP packets aremissing. The Content Collection function 412 can determine whether ornot to re-request any missing IP packets, or determine that the data canbe reconstructed without the missing packet(s). The determination ofre-request is in the exemplary embodiment service-dependent. Certainservices such as voice or audio can tolerate a certain amount of packetloss, while other services (such as data) require the receipt of allpackets in order to reconstruct the transmitted information.Accordingly, it is appreciated that the present invention may beutilized in both “lossy” and non-lossy contexts with equal success.

The Content Collection function 412 provides the collected IP packets tothe Packet Sequencing/Duplicate Detection and Removal/Jitter Mitigationfunction 414. In one embodiment, the Packet Sequencing/DuplicateDetection and Removal/Jitter Mitigation function 414 is responsible fororganizing the received IP packets according to the packet sequencenumber. In addition, any detected duplicate IP packets are removed, andany desired jitter management functionality on the received IP packetsis applied (such as for example discard or packets received outside of a“jitter window” as being received too late). The PacketSequencing/Duplicate Detection and Removal/Jitter Mitigation function414 provides the resultant IP packets 416 to the receive side for anyfurther required processing.

Referring to FIG. 5, an exemplary protocol structure for improved IPflow mobility and content distribution configured in accordance with oneembodiment of the present invention is illustrated. The transmit sideincludes a network layer 502, such as for example an IP layer. In oneimplementation, the network layer 502 is responsible for contentdistribution and QoS enforcement functionality discussed supra. Thenetwork layer 502 receives the IP layer service data units (SDU) from ahigher layer. The network layer 502 packages the received IP SDUs intoIP packets to route to the determined transmit-side protocol stacks 504of the available RATs. The IP packets are the IP (network) layer'spacket data units (PDU). The transmit-side protocol stacks 504 transmitthe IP packets over the air interface connecting to the receive-sideprotocol stack 506 of the respective receive RAT. The receive-sideprotocol stacks 506 provide the received IP packets to the receive sidenetwork layer 508. In one embodiment, the receive side network layer 508handles content collection and jitter management functionality asdiscussed above. For example, the jitter management functionalityincludes a buffer sized to be longer than the maximum one-waytransmission delay over the available data links.

After the receive side network layer 508 has processed the received IPpackets, the IP packets (i.e. PDUs) are provided to the appropriatelayer for further processing.

In the case of the same operator's networks, the foregoing functions liebetween the common IP layers associated with one of multiple radioaccess technologies of the network shared by the device. In the case ofdifferent operators' network, the content distribution and collectionfunction, in one implementation, lies outside of the radio accessnetwork protocols (and in the common core network, as illustrated byFIG. 6).

Referring to FIG. 6, an exemplary cross-network content distributionentity 602 is shown providing content to a client device 606 (e.g. userequipment (UP)) by communicating over a variety of networks 604. Thecontent distribution entity 602 may dynamically allocate IP flows to theclient device 606 via any of the suitable networks 604, as discussedelsewhere herein.

Methods

Referring now to FIG. 7, one embodiment of a generalized method 700 fordynamically allocating IP flows across multiple networks is illustrated.In one scenario, a client device (e.g., UE) is capable of communicatingover a multitude of possible RATs. For example, the client device may beable communicate with a network over an LTE RAT or an 802.11-based RAT.In one implementation, a cross-network content distribution entity isresponsible for allocating the IP flows across a variety of network RATsavailable to the client device.

As a brief aside, in an IP-based radio access network, an IP session isestablished or torn down after a data link layer connection isestablished or torn down respectively. Thus, a new IP connection needsto be established once a data link layer connection on any availableradio access networks for the client device is configured. Therefore, ifthe IP packets associated with multimedia content (such as videostreaming or VoIP) or any other IP-based application are scheduled for aparticular client device having several radio connections with thenetwork, the network layer packets can be distributed across theconnections which, for example, meet the QoS requirements of the servicebeing provided.

Referring back to FIG. 7, at step 702 of the method 700, data to bedynamically allocated to networks is received. In one embodiment, the IPflows are received in the form of IP packets. The IP packets may bereceived from the same flow, or from a variety of different flows. TheIP packets are for example downlink communications initiated by arequest from applications and/or services running on the client device.For instance, the data packets may be received from an applicationrequesting to stream video content with a content provider, orinitiating a voice call on the client device.

The IP packets of the received data packets are sequenced in order tofacilitate reorganization (described subsequently hereafter, at step712). In one implementation, the received packets of the IP flow aresequenced using information located in the header of the IP packets. Forexample, in the case of the Real-time Transport Protocol (RIP), the IPpackets may be sequenced using the sequence number and time stamp of theRTP header. Note that for example IPv4, IPv6, and User Datagram Protocol(UDP) do not carry a sequence in their respective headers. However, theTCP header does include a 32-bit sequence number that can be used tosequence and arrange the IP packets, and to detect lost or late packetsat the receiver. Thus, depending on the type of the IP packet (e.g.,IP/UDP/RTP/, IP/TCP, etc.), the sequence number of either the RTP of theTCP headers may be used for the purpose of sequencing the IP packets.Moreover, yet other protocols may be used consistent with the inventionin addition to those listed above.

As a brief aside, given the use of standard IP/UPD/RTP or IP/TCPprotocols over the data-plane of different radio interfaces, and thatthe checksum sequences in UDP and TCP headers are calculated based onthe application layer payloads, inserting a sequence number directlyinto the header would affect existing protocols. One salient advantageof the exemplary embodiments of the present invention is that by notdirectly inserting packet sequencing number within the received IPpackets, the packet may be sequenced without modifying the existingprotocols (e.g., compensating for the resolution of insertion of thepacket sequence with the check sum).

At step 704, the transmit parameters for the received IP flows aredetermined. In one embodiment, the transmit parameters areclassifications of the received IP packets. The classification may bebased on one or more of parameters, such as priority or importance ofthe particular IP packets (for example in terms of acceptabledegradation), minimum QoS requirements associated with the IP packets,service type (e.g. VoIP, audio/video streaming, etc.), amount ofresources required by the IP packets, and/or other service relatedparameters. It is readily apparent that the possible classifications arein no way limited to the aforementioned parameters, which are providedfor illustration only.

At step 706, the received IP flow is organized. In one embodiment, thereceived IP flow is organized to assign particular data of the receivedflow data is a network interface in order to be transmitted. The networkinterfaces may comprise any suitable RAT to communicate with over adesired network. The determined transmit parameters are used at least inpart to organize assignments of data to particular network interfaces.For example, the received data may have been classified according arequired minimum required data rate. Thus, the data in the exemplaryconfiguration will only be assigned to a network interface thatsupported the minimum required data rate.

In one implementation, the data is further assigned according to orbased upon feedback from the network interfaces. For example, thefeedback may include network interface availability, channel conditionsof the network link, inter-RAT interface among the available networkinterfaces, reliability of the network link, maximum delay over thenetwork link, etc. The feedback may be instantaneously provided, and/ormay be based on statistical analysis (e.g., the performance of a networklink over a certain period of time). The feedback is used in part tomake assignment decisions when organizing the received IP flow. Thefeedback may also be used to assess the quality and reliability of theradio link over the averages of the short term or long term possibilityof error over a corresponding network interface. The feedback allows fora determination of the amount of data that can be routed through eachavailable network interface.

One salient advantage of using feedback from the network interfaces isthat the data organization can account for varying link conditionsexperienced over time. For example, a network interface link mayexperience deterioration. In response, the received data may be assignedto a lower data rate network interface, or a network interface utilizinga lower modulation scheme. The data may also be repeated over thenetwork interface in order to improve reliability of the connection tocompensate for the deterioration of the link.

At step 708, the organized data is transmitted. In one embodiment, oncethe data has been distributed to the available network interfaces (basedon the data assignments), the data is transmitted over wireless networkinterfaces. The network interfaces may, depending on implementation,perform any requisite management of the transmission, such as forexample, automatic repeat request (ARQ) or hybrid automatic repeatrequest (HARQ), and any other link-specific error detection, correction,adaptation, or recovery performed in accordance with to networkinterface's protocols.

At step 710, the transmitted data is received. In one embodiment, thereceived data is collected and analyzed in order to determine whether ornot any data is missing that should have been otherwise received, andalso to detect any duplicate data received for removal. In oneimplementation, if any missing data is detected, the respective networkinterface responsible for receiving the data can be directed to send arequest for retransmission, or otherwise decide that no retransmissionis necessary. In one variant, the network interfaces responsible forreceiving the transmitted data are responsible for providing feedback tothe transmitting network interfaces such as, for example, qualityindications of the link, or errors in the data received.

At step 712, the received data is reorganized. In one embodiment, thedata is reorganized using sequencing information as discussed withrespect to step 704 above. The sequencing number is used to reorganizethe data into its proper order to create the IP flow received at step702, and to enable proper delivery of the IP flow to the targetdestination. It is appreciated, however, that other organizationtechniques (i.e., other than ordering or temporal sequencing) may beused consistent with the invention. For instance, packets may be orderedaccording to a priority (aside from any temporal aspects associatedtherewith), by payload type, size, etc.

While the foregoing discussion was cast in the context of a downlinkcommunication with a client device, the generalized methodologydescribed with respect to FIG. 7 is equally applicable in both downlinkand uplink directions. For example, in the uplink direction, the clientdevice would implement the functionality of the cross-network contentdistribution entity (such as monitoring and selecting the best availableradio links, and distributing the IP flows across those radio links).

Example Operation

Referring now to FIG. 8, one exemplary implementation of the method of700 of FIG. 7 is shown and described. Specifically, the exemplaryimplementation of FIG. 8 is described in the context of dynamicallyallocated IP flows across multiple RAT interfaces of a device. In onescenario, the device is a multi-radio solution capable of communicatingwith a LTE network, a WiMAX network, and an 802.11-based network. Whilethe following operation is described in relation to LTE, WiMAX, and802.11-based networks, it is readily appreciated that various aspects ofthe present invention are widely applicable to various forms of datacommunication and corresponding RATs.

At step 802, IP packets are received from the network layer of thedevice. The received IP packets are from various applications andservices running on the resident device.

The received IP packets are collected and provided to the packetsequencing function.

At step 804, the received IP packets are sequenced based on the servicecharacteristics of the IP packets. If the IP packets belong to a serviceimplementing TCP, then the IP packets are sequenced according to the TCPheader 32-bit sequence number. If the IP packets belong to a serviceimplementing RTP, then the IP packets are sequenced according to the RTPheader sequence number and time stamp information. The packetidentification numbers of the sequenced IP packets are provided to thedistribution function. The sequenced IP packets are provided to step 806for classification.

At step 806, the sequenced IP packets are classified according to the IPpacket's priority, minimum QoS requirements, service type, amount ofradio resources required to transmit, and/or other service-relatedparameters. Based on the classification of the IP packets, thecorresponding packet service requirements are provided to thedistribution function (see step 808).

At step 808, the distribution function maps the received classified IPpackets to the appropriate radio interface link. The appropriate radiointerface link is selected based on an algorithm, which considers thepacket service requirements of the respective IP packet against reportedavailable radio links and their condition. Only the radio connectionsthat can satisfy the minimum QoS requirements of the packets asindicated by their respective packet service requirements are consideredavailable radio links. The distribution function determines theconditions of the radio links by receiving radio resource managementreports (RRM) from the radio interfaces in addition to reports from thePacket Collection module at the receive side. The Packet Collectionmodule monitors the experienced packet loss and retransmission reportsfor missing packets. Thereafter, the distribution function can assignthe IP packets to the respective radio interfaces that can support theIP packets service requirements. By monitoring the quality of the radiolinks, the distribution function can dynamically adjust the allocationsamong the radio links as appropriate. In this manner, the distributionfunction provides the radio interfaces with the assigned IP packets andtheir respective packet identification; this information is used fortransmission over the radio link.

The IP packets are retrieved from each radio link, queued, and assembledaccording to their sequence number at the destination. The collectionfunction may further request transmission of any lost or delayed IPpackets through more reliable links and with more reliable transmissionformats if necessary. Depending on the importance of the payload inreconstruction of the content, some lost or delayed IP packets may betolerated.

Exemplary Client Apparatus

Referring now to FIG. 9, an exemplary embodiment of a user device orapparatus 900 to dynamically allocate IP flows across heterogeneousnetworks is illustrated. As used herein, the term “user device”includes, but is not limited to cellular telephones, smartphones (suchas for example an iPhone™ manufactured by the Assignee hereof), handheldor tablet computers, laptops, personal media devices (PMDs), or anycombinations of the foregoing. While a specific device configuration andlayout is shown and discussed, it is recognized that many otherconfigurations may be readily implemented by one of ordinary skill giventhe present disclosure, the apparatus 900 of FIG. 9 being merelyillustrative of the broader principles of the invention.

The processing subsystem 902 includes one or more of central processingunits (CPU) or digital processors, such as a microprocessor, digitalsignal processor, field-programmable gate array, RISC core, a basebandprocessor, or plurality of processing components mounted on one or moresubstrates. In some embodiments, one or more of the above-mentionedprocessors (e.g. the baseband processor) are further configured toimplement the dynamic allocation of data across heterogeneous networksmethods or protocols described previously herein.

The processing subsystem is coupled to non-transitory computer-readablestorage media such as memory 904, which may include for example SRAM,FLASH, SDRAM, and/or HDD (Hard Disk Drive) components. As used herein,the term “memory” includes any type of integrated circuit or otherstorage device adapted for storing digital data including, withoutlimitation, ROM. PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS,RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), and PSRAM. The processingsubsystem may also include additional co-processors, such as a dedicatedgraphics accelerator, network processor (NP), or audio/video processor.As shown, the processing subsystem 902 includes discrete components;however, it is understood that in some embodiments they may beconsolidated or fashioned in a SoC (system-on-chip) configuration.

The apparatus 900 further includes wireless interfaces 906 which areconfigured to transmit and receive signaling. For instance, in onevariant, an LTE (e.g., Release 8 or beyond) cellular interface isprovided, as well as a WLAN (e.g., IEEE Std. 802.11a/b/g/n/v/-2012compliant) interface.

The user device 900 further includes a user interface 908, such as forexample a “multi-touch” or other touch-screen user display and inputdevice of the type well known in the art. The present inventioncontemplates that one or more user inputs may be received via theinterface 908 to, inter alia, configure the foregoing IP flow mobilityfunctions of the invention from the user device side. For example, theuser might set preferences for the handling of their IP flows,priorities between types of data, and so forth, that can be used toconfigure the various processes and entities (e.g., the aforementionedcontent distribution or collection functions 304, 306). That being said,the invention also contemplates completely user-transparent variantswherein the content distribution, collection, prioritization, and otherfunctions are wholly handled via one or more computer programs residenton the user device (such as in the non-transitory storage mediumreferenced herein).

In one exemplary embodiment, the non-transitory computer-readablestorage media includes instructions which when executed by theprocessor, sequence and prioritize one or more data packets, andtransmit the data packets via a heterogeneous network according to thesequence and prioritization for each packet, as described supra withrespect to the exemplary embodiments. Similarly the storage media of theclient device 900 may include instructions which when executed by theprocessor, receive a plurality of data packets via a heterogeneousnetwork according to a sequence and prioritization for each packet, andre-sequence and re-prioritize one or more data packets, such as forexample in response to a request for streaming media from a networkserver.

Exemplary Server Apparatus

Referring now to FIG. 10, an exemplary embodiment of a server apparatus1000 supporting dynamic allocation of IP flow to/from a client device isillustrated. As used herein, the term “server” includes, but is notlimited to, network servers, macrocells, microcells, femtocells,picocells, wireless access points, or any combinations of the foregoing.While a specific device configuration and layout is shown and discussed,it is recognized that many other configurations may be readilyimplemented by one of ordinary skill given the present disclosure, theapparatus 1000 of FIG. 10 being merely illustrative of the broaderprinciples of the invention.

The processing subsystem 1002 includes one or more of central processingunits (CPU) or digital processors, such as a microprocessor, digitalsignal processor, field-programmable gate array, RISC core, or pluralityof processing components mounted on one or more substrates. Theprocessing subsystem is coupled to non-transitory computer-readablestorage media such as memory Z04, which may include for example SRAM,FLASH, SDRAM, and/or HDD (Hard Disk Drive) components. As used herein,the term “memory” includes any type of integrated circuit or otherstorage device adapted for storing digital data including, withoutlimitation, ROM. PROM, EEPROM, DRAM, SDRAM, DDR/2 SDRAM, EDO/FPMS,RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), and PSRAM. The processingsubsystem may also include additional co-processors. As shown, theprocessing subsystem 1002 includes discrete components; however, it isunderstood that in some embodiments they may be consolidated orfashioned in a SoC (system-on-chip) configuration.

The apparatus 1000 further includes one or more wireless interfaces 1006which are configured to receive/send transmissions from/to clientdevices (including connection request responses). A plurality ofwireline “back end” interfaces 1008 are also provided for communicationwith other network entities, such as for example an Ethernet(10/100/1000/10,000 Mbps) interface, or optical interface. Otherinterfaces may be used for such back-end communications, including forinstance IEEE Std. 1394, Thunderbolt, Wi-Fi, WiMAX (IEEE Std. 802.16),and so forth.

In one exemplary embodiment, the non-transitory computer-readablestorage media of the apparatus 1000 includes instructions which whenexecuted by the processor, sequence and prioritize one or more datapackets, transmit the data packets via a heterogeneous network accordingto the sequence and prioritization for each packet. The storage media1004 further includes instructions which, when executed by theprocessor, receive a plurality of data packets via a heterogeneousnetwork according to a sequence and prioritization for each packet; andre-sequence and re-prioritize one or more data packets. Accordingly, inone variant of the invention, the transmission and receptioncapabilities of the network apparatus 1000 and the aforementioned userdevice 900 are largely symmetric and “mirror imaged” (i.e., the server1000 and the user device 900 can each provide enhanced heterogeneous IPflow mobility on the transmission side, and likewise receive flows whichhave been enhanced from the other). It will be appreciated, however,that the device configurations can also be asymmetric or heterogeneous,such as where the server 1000 is given more capability than the userdevice (due to its “thicker” processing capability and power supply),and the user device offloads some of its processing burden to theserver.

It will be recognized that while certain aspects of the invention aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of theinvention, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the invention disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the invention as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the invention. Theforegoing description is of the best mode presently contemplated ofcarrying out the invention. This description is in no way meant to belimiting, but rather should be taken as illustrative of the generalprinciples of the invention. The scope of the invention should bedetermined with reference to the claims.

What is claimed is:
 1. A method for dynamically allocating IP flowsacross heterogeneous network interfaces, the method comprising: at asource device: sequencing portions of data to be transmitted via two ormore heterogeneous network interfaces; classifying the portions of dataaccording to one or more parameters; assigning the portions of data tothe two or more heterogeneous network interfaces based at least in parton a classification of the portions of data and at least in part onmonitored operational conditions that include results from monitoringrequests received from at least one of the two or more heterogeneousnetwork interfaces; and transmitting the assigned portions of data viathe two or more heterogeneous network interfaces.
 2. The method of claim1, wherein the sequencing of the portions of data enables reconstructionof the portions of data transmitted via the two or more heterogeneousnetwork interfaces.
 3. The method of claim 1, wherein the assigningfurther comprises additionally assigning the portions of data based atleast in part on coordinating with individual schedulers of at least oneof the two or more heterogeneous network interfaces.
 4. The method ofclaim 1, wherein the sequencing of the portions of data is based atleast in part on using a sequence number that is part of a transportprotocol.
 5. The method of claim 1, wherein the heterogeneous networkinterfaces comprise at least (i) a cellular data-enabled interface, and(ii) a wireless local area network (WLAN) interface.
 6. A mobile userwireless apparatus, comprising: a processor; at least first and secondwireless interfaces coupled to the processor; and a storage devicecoupled to the processor, the storage device storing executableinstructions that, when executed by the processor, cause the mobile userwireless apparatus to dynamically allocate packet data flows across thefirst and second wireless interfaces by: sequencing portions of data tobe transmitted via the first and second wireless interfaces;characterizing the portions of data according to one or more parameters;assigning the portions of data to the first and second wirelessinterfaces based at least in part on a characterization of the portionsof data and at least in part on monitored operational conditions thatinclude results from monitoring requests received from at least one ofthe first and second wireless interfaces; and transmitting the assignedportions of data via the first and second wireless interfaces.
 7. Themobile user wireless apparatus of claim 6, wherein: the first and secondwireless interfaces comprise (i) a cellular data-enabled interface, and(ii) a wireless local area network (WLAN) interface; and the portions ofdata comprise Internet Protocol (IP) data assembled using a transportprotocol that includes packet sequence data that is used in at least thesequencing of the portions of data.
 8. The mobile user wirelessapparatus of claim 6, further comprising assigning the portions of datato the first and second wireless interfaces based at least in part oncoordinating with individual schedulers of at least one of the first andsecond wireless interfaces.
 9. The mobile user wireless apparatus ofclaim 6, wherein the sequencing of the portions of data is based atleast in part on using a sequence number that is part of a transportprotocol.
 10. The mobile user wireless apparatus of claim 6, wherein theexecution of the executable instructions is further configured to causethe mobile user wireless apparatus to: receive first and secondpluralities of data packets via the first and second wirelessinterfaces, respectively; evaluate the first and second pluralities ofdata packets; and based at least in part on evaluating the first andsecond pluralities of data packets, assemble the first and secondpluralities of data packets into a common packet data flow.
 11. A mobileuser wireless apparatus, comprising: a processor; at least first andsecond wireless interfaces coupled to the processor; and logic circuitsconfigured to dynamically allocate packet data flows across the firstand second wireless interfaces by: obtaining feedback information from areceiver apparatus regarding quality or reliability of at least one ofthe first and second wireless interfaces; selectively allocating aportion of a first packet data flow via at least one of the first andsecond wireless interfaces based at least in part on the feedbackinformation; monitoring operational conditions of the first and secondwireless interfaces, wherein the monitored operational conditionsinclude results from monitoring requests received from at least one ofthe first and second wireless interfaces; and transmitting the allocatedportion of the first packet data flow via at least one of the first andsecond wireless interfaces based on the selective allocation, whereineach the first and second wireless interfaces operate in accordance withone or more radio access technologies.
 12. The mobile user wirelessapparatus of claim 11, wherein the selective allocation comprisesevaluating the feedback information to determine a sufficiency of atleast one of the first and second wireless interfaces to meet minimumquality-of-service (QoS) requirements associated with the first packetdata flow, wherein the sufficiency of at least one of the first andsecond wireless interfaces to meet minimum the quality-of-service (QoS)requirements associated with the first packet data flow is determined inpart by coordinating with individual schedulers of the first and secondwireless interfaces.
 13. A wireless network apparatus, comprising: aprocessor; at least first and second wireless interfaces coupled to theprocessor; and computerized logic circuits configured to dynamicallyallocate packet data flows across the first and second wirelessinterfaces by: selectively allocating at least a portion of a firstpacket data flow via at least one of the first and second wirelessinterfaces based at least in part on information relating to one or moreattributes of the first packet data flow; monitoring operationalconditions of the first and second wireless interfaces, wherein themonitored operational conditions include results from monitoringrequests received from at least one of the first and second wirelessinterfaces; and transmitting the allocated portion of the first packetdata flow via at least one of the first and second wireless interfacesbased on the selective allocation, wherein the computerized logiccircuits are further configured to operate substantially at a networklayer so as to be independent of lower-layer functions.
 14. The wirelessnetwork apparatus of claim 13, wherein the lower layer functionscomprise at least media access control (MAC) layer packet data unit(PDU) scheduling and transmission functions corresponding to respectiveones of the first and second wireless interfaces.
 15. The wirelessnetwork apparatus of claim 14, wherein the network layer comprises alayer within which an Internet Protocol (IP) operates, and the firstpacket data flow comprises a plurality of IP packets encapsulated in atransport protocol comprising sequence information relating to theplurality of IP packets.
 16. The wireless network apparatus of claim 13,wherein the selective allocation is based at least in part on a statusof battery power of one or more mobile devices.
 17. A network apparatus,comprising: a processor; at least first and second wireless interfacescoupled to the processor; and a storage device coupled to the processor,the storage device storing executable instructions that, when executedby the processor, cause the network apparatus to dynamically allocatepacket data flows across the first and second wireless interfaces by:receiving via one of the first and second wireless interfaces a requestfor a packet data flow from a mobile device; sequencing portions of thepacket data flow to be transmitted via the first and second wirelessinterfaces; characterizing the portions of the packet data flowaccording to one or more parameters; assigning the portions of thepacket data flow to the first and second wireless interfaces based atleast in part on a characterization of the portions of the packet dataflow; monitoring operational conditions of the first and second wirelessinterfaces, wherein the monitored operational conditions include resultsof monitoring requests received from at least one of the first andsecond wireless interfaces; and transmitting the assigned portions ofthe packet data flow via the first and second wireless interfaces to themobile device.
 18. The network apparatus of claim 17, wherein theexecution of the executable instructions is further configured to causethe network apparatus to receive and evaluate feedback information fromthe mobile device, the feedback information being related to at leastone of channel quality or reliability associated with at least one ofthe first and second wireless interfaces, wherein the feedbackinformation is based in part on coordinating with individual schedulersof at least one of the first and second wireless interfaces.